For example, processing a donation immediately requires that multiple iParts are defined in a single content record. It does not matter the order in which the iParts are defined on the page. In the scenario outlined below, where the Donation Creator is the first iPart displayed on the page and the Submit Order Button Link is the last iPart displayed, the Commit sequence value controls the order in which the iParts are processed. When the donation is "submitted" from the content record, execution control is given to each iPart based on the Commit sequence value shown in parentheses:
Notes
Related Helpsite topics